Update setup_databases call to handle >3.1#859
Closed
hugorodgerbrown wants to merge 1 commit intopytest-dev:masterfrom
yunojuno:master
Closed
Update setup_databases call to handle >3.1#859hugorodgerbrown wants to merge 1 commit intopytest-dev:masterfrom yunojuno:master
hugorodgerbrown wants to merge 1 commit intopytest-dev:masterfrom
yunojuno:master
Conversation
Author
|
Existing tests are failing (unrelated to this PR): |
Author
|
Further investigation of the test failures - I've rolled back through from |
Member
|
Thanks @hugorodgerbrown, this was handled by #857 which took a similar approach. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #858
A breaking change in the current master on Django has added a mandatory
time_keeperkwarg to thedjango.test.utils.setup_databasesfunction signature. This is aTimeKeeperobject which is used to record how long it takes to setup test databases. It is used internally by the Django tests themselves. ANullTimeKeeperobject is available if timings are not required. I have used theNullTimeKeeperin this PR (as I don't think setup timing is a core pytest requirement?)There are no additional tests for this change, as its main impact is in fixing the existing test suite. There should be a reduction in the number of current failures on
py*_djmasterbuilds. I currently get these failures when runningmake testlocally against the latest master of Django: